Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1393

reference
617-tree-1
name
1393
tree-preservation-order

undefined

617-tpo-1
uprn
address-text
point
POINT (-1.023443 50.881018)
geometry
MULTIPOLYGON (((-1.023372 50.881010,-1.023375 50.881024,-1.023385 50.881037,-1.023400 50.881047,-1.023420 50.881053,-1.023442 50.881056,-1.023464 50.881054,-1.023484 50.881048,-1.023500 50.881038,-1.023510 50.881025,-1.023514 50.881012,-1.023511 50.880998,-1.023501 50.880985,-1.023485 50.880975,-1.023466 50.880968,-1.023444 50.880966,-1.023422 50.880968,-1.023402 50.880974,-1.023386 50.880984,-1.023376 50.880996,-1.023372 50.881010)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL